API

Product APIs

PUT product/units/{productUnitId}

Update serial product unit.

HTTP method PUT
URI https://api.rambase.net/product/units/{productUnitId}
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {productUnitId} Product unit identifier
Integer, minimum 100000
Custom fields Custom fields supported
Successful HTTP status code 200
API resource identifier 3472, version 5

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<ProductUnit
ProductUnit

This field is optional.

>
2
     <SerialNumber
SerialNumber

Serial number

This field is optional.

>{String}</SerialNumber>
3
     <Marking
Marking

Product unit's marking text

This field is optional.

>{String}</Marking>
4
</ProductUnit>
1
{
2
     "productUnit
ProductUnit

This field is optional.

": {
3
          "serialNumber
SerialNumber

Serial number

This field is optional.

": "{String}",
4
          "marking
Marking

Product unit's marking text

This field is optional.

": "{String}"
5
     }
6
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$showCustomFields Boolean, optional Set to "true" to include custom fields. Default value is false.

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields. Fields colored in grey is expandable fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
1

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 100858 HTTP 400 No LCM found
Error 101420 HTTP 404 Setting definition not found